Working with Data, Visualizations, and Filters Panes in Microsoft Power BI

Course: Microsoft Power BI Training

Topic: Working with Data, Visualizations, and Filters Panes

Course Link: Microsoft Power BI Training at JustAcademy

Demo Link: Register for a Free Course Demo

JustAcademy Website: Visit JustAcademy

1. Introduction to Power BI Report Development

Microsoft Power BI is a business intelligence and data visualization platform used to connect to data sources, transform data, build interactive reports, and share business insights. It enables users to convert raw information into meaningful visual representations such as charts, tables, cards, maps, and dashboards.

When developing a report in Power BI Desktop, three important areas help users build and control report content: the Data pane, the Visualizations pane, and the Filters pane. Understanding these areas is essential for creating reports that are accurate, interactive, and easy to understand.

• Data pane: Displays available tables, columns, measures, and other model fields that can be used in a report.
• Visualizations pane: Helps users select visual types and configure the fields, formatting, and properties of a visual.
• Filters pane: Controls which data appears in a visual, on a report page, or throughout the report.

These panes work together. Users select fields from the Data pane, create or configure a visual using the Visualizations pane, and refine the information displayed through the Filters pane.

2. Learning Objectives

After completing this topic, learners should be able to:

• Understand the purpose of the Data, Visualizations, and Filters panes.
• Identify tables, columns, numeric fields, date fields, and measures.
• Add fields to charts, tables, cards, and other visualizations.
• Select appropriate visual types for different analytical requirements.
• Configure visual fields, aggregations, labels, legends, axes, and formatting.
• Apply visual-level, page-level, and report-level filters.
• Understand the difference between filters, slicers, and visual interactions.
• Use basic filtering techniques to investigate business performance.
• Troubleshoot common issues involving missing fields, incorrect aggregations, and unexpected filter results.
• Develop an interactive report using a practical business dataset.

3. Understanding the Power BI Desktop Interface

Power BI Desktop provides a report-building environment containing the report canvas, navigation views, ribbon, and panes. The exact placement and available options may vary depending on the Power BI Desktop version and interface settings.

3.1 Report Canvas

The report canvas is the main workspace where users place and arrange charts, tables, cards, slicers, and other visual elements.

For example, a sales report may contain a total sales card, a monthly sales line chart, a category comparison bar chart, and a detailed transaction table.

3.2 Data Pane

The Data pane lists the fields available in the semantic model. Users can expand tables, locate fields, and add those fields to visuals.

3.3 Visualizations Pane

The Visualizations pane provides controls for creating and configuring report visuals. Depending on the interface and selected visual, users may find visual-type options, field wells, and formatting settings.

3.4 Filters Pane

The Filters pane provides filter controls for individual visuals, report pages, and the entire report. It allows users to limit the records used in a visual without necessarily deleting any data from the underlying model.

3.5 Report, Table, and Model Views

• Report view: Used to create and arrange report pages and visualizations.
• Table view: Used to inspect table data in a tabular format.
• Model view: Used to inspect and manage relationships between tables and other model structures.

The available views and interface controls can vary by version and workspace configuration. For further reference, see the Microsoft Power BI report editor overview.

4. Working with the Data Pane

The Data pane is the starting point for adding data to a report. It organizes fields according to their tables and helps users identify the information available for analysis.

4.1 What the Data Pane Contains

• Tables: Collections of related data, such as Sales, Products, Customers, and Calendar.
• Columns: Fields containing values such as product names, sales amounts, regions, and transaction dates.
• Measures: Calculations created using DAX to return values based on the current filter context.
• Hierarchies: Groupings of related fields that support navigation through levels, such as Year, Quarter, Month, and Day.

4.2 Example of a Sales Table

This example includes transaction identifiers, dates, product categories, regions, quantities, and sales values. Each field can be used for a different analytical purpose.

4.3 Identifying Field Data Types

Data types influence how Power BI interprets fields and which operations are available.

Always verify a field's data type before using it in a visual. For example, a date stored as text may not behave correctly in date slicers or time-based charts.

4.4 Adding Fields to a Visual

Fields can commonly be added to visuals by selecting them in the Data pane or dragging them into the appropriate field area or directly onto the report canvas. The result depends on the selected visual and the field type.

1. Open Power BI Desktop and load a dataset.
2. Switch to Report view.
3. Locate the required table in the Data pane.
4. Expand the table to display its fields.
5. Select or drag a field onto the canvas or into an existing visual.
6. Review the automatically generated visual and adjust its configuration if necessary.

For example, adding Sales Amount to an empty report canvas may create a visual that summarizes the field. Adding Region can introduce a category breakdown, depending on the visual selected and the way the field is added.

4.5 Columns Versus Measures

A column stores a value for each row of a table, while a measure calculates a result based on the current evaluation context.

4.6 Creating a Basic DAX Measure

A measure can calculate total sales from the Sales Amount column.

Total Sales = SUM(Sales[Sales Amount])

To create this measure:

1. Select the Sales table or an appropriate home table in the model.
2. Choose the New measure command.
3. Enter the DAX expression in the formula bar.
4. Confirm the formula and check that the measure appears in the Data pane.
5. Add the measure to a card, chart, or table.

The measure returns the sum of Sales Amount within the current filter context. If the report is filtered to the West region, the measure returns the sales total for the West region rather than necessarily returning the overall total.

5. Understanding the Visualizations Pane

The Visualizations pane helps users choose a visual type and configure how data is presented. A suitable visual makes comparisons, trends, relationships, and exceptions easier to understand.

5.1 Common Visualization Types

Choose a visual based on the analytical question rather than appearance alone. For a small number of category comparisons, a bar chart is often easier to interpret than a pie chart. For a time series, a line chart is generally more suitable than a table of isolated values.

For more information, consult Microsoft's Power BI visualization types documentation.

5.2 Creating a Chart

To create a basic chart:

1. Open the report canvas.
2. Select a suitable chart type in the Visualizations pane.
3. Locate the required category and numeric fields in the Data pane.
4. Add the category to the chart's category or axis field area.
5. Add the numeric field or measure to the value field area.
6. Review the result and check whether the chart answers the intended question.
7. Use the formatting options to improve readability.

For example, to create Sales by Region, use Region as the category and Total Sales as the value. Each region will be represented by a bar or column whose length or height reflects the sales value.

5.3 Understanding Visual Field Wells

Depending on the visual and Power BI interface version, the field configuration area may contain different roles.

• X-axis or category: Identifies the categories or positions along the horizontal axis.
• Y-axis or values: Contains numeric values, measures, or other supported fields.
• Legend: Separates data into series or groups using colors or symbols.
• Tooltips: Displays additional information when the user points to a data point.
• Small multiples: Creates separate panels for categories when supported by the selected visual.
• Details or other visual-specific roles: Provide additional grouping or analytical behavior where supported.

The available field roles vary by visual. If a field cannot be placed into a particular area, verify that the chosen visual supports the field's data type and role.

5.4 Choosing the Correct Aggregation

Numeric columns are often summarized automatically. Power BI may use Sum, Average, Minimum, Maximum, or Count, depending on the field and visual configuration.

For example, summing Order ID usually does not provide a useful business result because an identifier is not a measure of performance. Counting orders or counting distinct Order ID values is more appropriate when the requirement is to determine the number of orders.

5.5 Formatting Visuals

Formatting improves clarity and consistency. Depending on the selected visual, common formatting options include:

• Title text and subtitle settings.
• Font size, color, and text alignment.
• Data labels and display units.
• Axis titles, scale, and labels.
• Legend position and title.
• Background, borders, and visual effects.
• Number formats, decimal places, and currency symbols.
• Tooltips and conditional formatting where supported.

To format a visual, select it on the canvas and open its formatting controls in the Visualizations pane or the relevant formatting interface. The exact location of these controls can differ across versions.

For a sales chart, use a meaningful title such as “Total Sales by Region,” format monetary values consistently, and avoid excessive colors or unnecessary visual effects.

6. Understanding the Filters Pane

The Filters pane restricts which data is included in a visual, on a report page, or across the report. Filters are essential when users need to focus on a particular region, product, time period, customer group, or business condition.

Filtering changes the subset of data used for analysis. It does not usually delete the underlying records from the source or model.

6.1 Why Filters Are Important

• Focus reports on relevant business questions.
• Reduce visual clutter by excluding irrelevant categories.
• Compare performance across selected regions or time periods.
• Investigate high-performing and low-performing segments.
• Build focused views for different reporting needs.
• Support interactive analysis without creating a separate report for every scenario.

6.2 Types of Filters

6.3 Visual-Level Filters

A visual-level filter applies to a specific visual. Other visuals on the same page can remain unaffected unless the same condition is applied to them through another filter or interaction.

Example: A report page contains total sales by region and total sales by product. If a visual-level filter is applied to the region chart to show only West and East, the product chart does not automatically inherit that visual-level filter merely because it is on the same page.

To apply a visual-level filter:

1. Select the visual on the report canvas.
2. Locate the Filters pane.
3. Find or add the relevant field in the filters for that visual.
4. Choose the required filter type or values.
5. Apply the condition if the interface requires it.
6. Verify that the selected visual displays the expected data.

6.4 Page-Level Filters

A page-level filter applies to visuals on a particular report page. It is useful when a page is intended to represent one period, business unit, or product group.

Example: Apply a page-level filter to Order Date so that the Sales Overview page displays only records from 2026. The filter affects the relevant visuals on that page, subject to model relationships and visual behavior.

6.5 Report-Level Filters

A report-level filter applies across report pages within the filter's scope. It can be used to establish a shared restriction, such as displaying data for a particular division or excluding a category from the entire report.

Example: If management wants to review only the Consumer Products business unit, a report-level filter can establish that restriction across applicable pages.

Before applying a report-level filter, verify whether all report pages should use the same restriction. A global filter can change totals and comparisons throughout the report.

7. Common Filter Types and Conditions

Power BI provides different filter controls depending on the field type and interface. Common options include selecting individual values, applying conditions, and using advanced filtering rules.

7.1 Basic Filtering

Basic filtering allows users to select or deselect specific values from a list.

Example: Select West and North in the Region field to display records for those regions, while excluding East and South.

7.2 Advanced Filtering

Advanced filtering supports conditions such as is greater than, is less than, contains, begins with, or other operators appropriate to the data type.

Examples:

• Sales Amount is greater than 50,000.
• Product contains “Laptop”.
• Region is not “South”.

Available operators depend on the field's data type and the selected filter control.

7.3 Date Filtering

Date fields can be filtered using date values or supported date conditions. Depending on the field and interface, users may filter by a specific date, a range, or relative periods.

Examples include:

• Orders placed during January 2026.
• Transactions within a selected date range.
• Records from the current month using an appropriate relative date filter.

Check whether the field is stored as a genuine Date or Date/Time type. A text field that merely looks like a date may not provide the expected date-filtering options.

7.4 Top N Filtering

Top N filtering helps identify the highest- or lowest-performing items based on a selected measure.

Example: Show the top five products by Total Sales.

1. Select the product chart.
2. Add the Product field to the visual-level filters if necessary.
3. Choose the Top N filter option where available.
4. Specify Top and enter 5.
5. Use Total Sales as the ranking measure.
6. Apply the filter and verify the results.

Top N results depend on the selected measure and the current filter context. If several products have equal values near the cutoff, the displayed result may require closer review.

7.5 Filtering Blank Values

Blank values can occur because information is missing, records do not match related tables, or a calculation returns blank. Users can filter out blanks when they are not relevant to the analysis, but should first investigate why they exist.

Removing blanks without understanding their meaning may hide data quality issues or incomplete business records.

8. Applying Filters Step by Step

The following procedure demonstrates how to filter a sales report by region.

1. Load the Sales table into Power BI Desktop.
2. Create a chart using Region and Total Sales.
3. Select the chart on the report canvas.
4. Open the Filters pane.
5. Locate Region under the visual-level filters, or add it to that section if required.
6. Select the desired region values.
7. Observe how the chart changes.
8. Clear or modify the filter to compare the result with the unfiltered chart.

For a page-level filter, use the page-level section instead. For a report-level filter, use the report-level section. The section where a field is placed determines the scope of the filter.

9. Filters Pane Versus Slicers

Filters and slicers both restrict data, but they serve different report-design purposes.

9.1 Creating a Slicer

1. Select an empty area on the report canvas.
2. Choose the Slicer visual.
3. Add a field such as Region, Year, or Product Category.
4. Choose a suitable presentation, such as a list, dropdown, or supported date control.
5. Test the slicer by selecting different values.
6. Check which visuals respond to the slicer and configure interactions if necessary.

A slicer is useful when viewers should be able to change the report's focus without opening the Filters pane. For example, a Region slicer can allow a manager to compare West, North, South, and East sales interactively.

10. Understanding Filter Context and Visual Interactions

Power BI evaluates measures according to the filter context created by filters, slicers, visual selections, and model relationships. Understanding filter context is important because the same measure can return different results in different report locations.

10.1 Filter Context Example

Consider the measure:

Total Sales = SUM(Sales[Sales Amount])

This measure can return different results depending on the context:

• On a card without additional restrictions, it returns the total for the applicable dataset and model context.
• On a chart grouped by Region, it returns the total for each region.
• With a Year slicer set to 2026, it returns sales for the selected year where the model supports that date relationship.
• With both Year and Region filters, it returns sales for the intersection of the selected conditions.

10.2 Cross-Filtering and Cross-Highlighting

When a user selects a data point in one visual, Power BI may filter or highlight related data in other visuals on the same page. The behavior depends on the visual types, model relationships, and configured visual interactions.

For example, selecting the West region in a bar chart may cause a product chart to display only West-region sales or highlight the West contribution. A card may update to show the selected region's sales.

10.3 Editing Visual Interactions

Report authors can configure how visuals interact when supported by the report editor.

1. Select the visual that will initiate the interaction.
2. Open the relevant visual-interaction controls, commonly available through the Format ribbon in Power BI Desktop.
3. Inspect the interaction options displayed over the other visuals.
4. Choose an appropriate behavior, such as filtering, highlighting, or no interaction, where supported.
5. Test the report by selecting different data points.

Use interactions intentionally. If selecting one chart unexpectedly changes another, inspect the interaction settings and the model relationships.

11. Practical Example: Building a Sales Analysis Report

Assume a business has sales transaction data containing Order ID, Order Date, Product, Region, Quantity, Unit Price, and Sales Amount. The objective is to create an interactive report for sales managers.

11.1 Step 1: Load the Data

Import the sales dataset using the appropriate connector. Review the columns in Power Query or the model and confirm that dates, numbers, currency values, and text categories have appropriate data types.

11.2 Step 2: Create a Total Sales Measure

Total Sales = SUM(Sales[Sales Amount])

This measure provides the total sales amount within the current context.

11.3 Step 3: Create a Total Quantity Measure

Total Quantity = SUM(Sales[Quantity])

This measure calculates the total quantity sold. It should not be confused with the number of orders or unique customers.

11.4 Step 4: Create a Sales Card

1. Add a Card visual to the canvas.
2. Place Total Sales in the card's value field.
3. Format the value as currency or the appropriate monetary unit.
4. Set a clear title such as “Total Sales”.

11.5 Step 5: Create Sales by Region

1. Add a bar chart.
2. Use Region as the category.
3. Use Total Sales as the value.
4. Sort the chart by Total Sales when that comparison is useful.
5. Add data labels if they improve readability.

11.6 Step 6: Create a Monthly Trend

1. Add a line chart.
2. Place Order Date on the horizontal axis.
3. Use Total Sales as the value.
4. Choose an appropriate date hierarchy or date granularity.
5. Format the axis and title so the time period is clear.

11.7 Step 7: Create a Product Table

Add a table visual containing Product, Total Quantity, and Total Sales. This table allows users to review the values behind the summary charts.

11.8 Step 8: Add a Region Slicer

Add a slicer containing Region. Select different regions and verify that the card, chart, line chart, and table respond as intended.

11.9 Step 9: Apply a Page-Level Date Filter

Use the Order Date field in the page-level filter section to limit the page to the required reporting period. Verify that the date filter affects the relevant visuals.

11.10 Step 10: Validate the Results

• Compare Total Sales with the expected total from the source data.
• Check that regional totals reconcile with the overall total when all regions are included and no other conditions change the context.
• Confirm that the monthly chart uses the correct date field and granularity.
• Test each slicer and filter combination.
• Ensure the report titles and units are clear.

12. Data Pane Best Practices

• Use clear and meaningful table and field names.
• Organize related fields into suitable tables.
• Hide technical columns from report view when report consumers do not need them, while preserving fields required for model operations.
• Verify data types before building visuals.
• Use explicit DAX measures for important business calculations.
• Distinguish numeric identifiers from values intended for aggregation.
• Keep date fields consistent and use a suitable date table when the analysis requires reliable time intelligence.
• Use descriptive measure names such as Total Sales, Average Order Value, and Total Quantity.
• Format measures with appropriate decimal places, percentages, or currency settings.

13. Visualization Best Practices

• Choose visuals based on the question being answered.
• Use bar or column charts for category comparisons.
• Use line charts for trends over time.
• Use cards for a small number of important metrics.
• Use tables and matrices when users need exact values or structured details.
• Avoid displaying too many categories in one chart.
• Use consistent colors and formatting throughout the report.
• Label axes and units clearly.
• Use data labels when they improve comprehension, not simply because they are available.
• Check that sorting reflects the analytical purpose.
• Use accessible contrast and avoid relying only on color to communicate meaning.
• Provide informative titles that explain the measure and grouping.

14. Filters Pane Best Practices

• Apply filters at the narrowest appropriate scope.
• Use visual-level filters when only one visual should be restricted.
• Use page-level filters when the whole page should represent the same reporting period or category.
• Use report-level filters only when the restriction should apply across relevant pages.
• Use slicers for important selections that report viewers should control easily.
• Make restrictive filters visible or clearly document their effect.
• Review filter interactions when totals appear unexpected.
• Check for conflicting filters at different scopes.
• Test reports with different selections before publishing.
• Do not filter out blanks or outliers without understanding their business meaning.

15. Common Problems and Troubleshooting

15.1 A Field Does Not Appear in the Data Pane

Possible causes: The table is collapsed, the field is hidden, the source data was not loaded as expected, or the model has not been refreshed.

Solutions:

• Expand the relevant table.
• Check whether the field is hidden in report view.
• Inspect the source query and model.
• Refresh the data when appropriate.
• Confirm that the correct table was loaded.

15.2 A Chart Displays a Total Instead of Categories

Possible causes: The chart contains a measure but no category field, or the category field was placed in the wrong field well.

Solutions:

• Add the appropriate category field, such as Region or Product.
• Confirm that the selected visual supports the field.
• Verify that the field is configured in the correct axis or category area.

15.3 Values Are Summed Incorrectly

Possible causes: A field uses an unsuitable aggregation, contains duplicate records, or represents an identifier rather than a numeric business measure.

Solutions:

• Inspect the column's data type.
• Change the aggregation to the appropriate operation.
• Use a DAX measure where the business definition requires explicit logic.
• Check duplicate records and the data model.

15.4 A Filter Does Not Affect All Visuals

Possible causes: The filter was added at visual level, visual interactions are disabled, or the fields do not have the expected model relationship.

Solutions:

• Check whether the filter is visual-level, page-level, or report-level.
• Review visual interaction settings.
• Inspect model relationships and filter directions.
• Confirm that the selected fields are connected through the model as expected.

15.5 A Slicer Does Not Filter a Chart

Possible causes: The slicer interaction is disabled, the slicer field is unrelated to the chart's data, or the model relationship does not propagate the filter as expected.

Solutions:

• Inspect the slicer's interactions with the target visual.
• Verify relationships between the tables containing the slicer field and chart values.
• Review whether the relationship is active and whether the model design supports the intended filter flow.
• Test the slicer with a simple table visual to isolate the issue.

15.6 Date Filters Behave Unexpectedly

Possible causes: The date field is stored as text, the wrong date column is being used, or the date hierarchy is not configured as expected.

Solutions:

• Confirm that the field uses a Date or Date/Time data type.
• Check the selected date hierarchy level.
• Verify the date range in the filter.
• Check the date table and its relationship when time-based calculations depend on it.

15.7 The Report Shows Unexpectedly Low or High Totals

Possible causes: Multiple filters are active, relationships produce unexpected results, data is duplicated, or the measure does not match the intended business definition.

Solutions:

• Inspect the visual, page, and report filter sections.
• Clear temporary selections and compare totals.
• Validate the source data and relationships.
• Check the DAX measure and the aggregation logic.
• Compare the report result with a known source total.

16. Filters, Relationships, and Data Model Design

Filters operate within the Power BI semantic model. Relationships determine how filters can propagate between connected tables, so the Data, Visualizations, and Filters panes cannot be understood completely without a basic knowledge of data modeling.

16.1 Example of a Simple Data Model

A sales model might include the following tables:

• Sales: Transaction records, order dates, product keys, quantities, and sales amounts.
• Products: Product keys, product names, categories, and brands.
• Customers: Customer keys, customer names, and customer segments.
• Calendar: Dates, years, quarters, and months.

Relationships connect matching keys between the Sales table and relevant dimension tables. A Region, Product Category, or Calendar Year filter can then affect sales calculations when the relationships and measure logic support that behavior.

16.2 Why Relationships Matter

If the model lacks an appropriate relationship, selecting a product category may not filter sales amounts as expected. Incorrect or ambiguous relationships can also produce confusing totals.

When a filter does not work as expected, inspect the model instead of assuming that the Filters pane is malfunctioning.

17. Understanding the Difference Between Filters and Data Transformation

Filtering in a report is different from filtering rows during data preparation.

Use report filters to support interactive analysis. Use Power Query transformations when data must be cleaned, standardized, or deliberately excluded as part of the data preparation process.

18. Practical Scenario: Regional Sales Analysis

A company wants to compare sales performance across four regions: North, South, East, and West. The report must show overall sales, regional performance, monthly trends, and product-level details.

18.1 Report Requirements

• Display total sales in a card.
• Compare sales by region in a bar chart.
• Show monthly sales trends in a line chart.
• Display product-level sales in a table.
• Provide a Region slicer.
• Allow users to focus on a selected year.
• Support investigation of individual products and regions.

18.2 Recommended Configuration

18.3 Expected Outcome

When the user selects West in the Region slicer, the report should show West-region results in visuals that are configured to respond to the slicer. When the user changes the year selection, the relevant values should reflect the selected period. The product table can then help identify which products contribute most to the selected region's performance.

The final report should be tested to confirm that all visuals, filters, and slicers behave consistently with the intended business rules.

19. Performance and Report Usability

A report should be easy to use and should respond efficiently to user selections. Excessive visuals, complicated measures, inefficient model relationships, and unnecessarily detailed data can affect report performance.

• Use a well-structured data model.
• Remove unused columns during data preparation when appropriate.
• Prefer clear measures that express business calculations directly.
• Avoid placing too many visuals on one page.
• Use slicers only where they provide meaningful control.
• Keep filters and titles understandable.
• Test performance with realistic data volumes.
• Use Performance Analyzer when investigating slow visuals in Power BI Desktop.
• Review visual interactions and measure complexity if the report becomes slow.

20. Exercises for Practice

Exercise 1: Explore the Data Pane

Load a sales dataset and identify all tables, text columns, numeric columns, date fields, and measures. Write down the purpose of each important field.

Exercise 2: Create a Sales Chart

Create a bar chart showing Total Sales by Region. Add data labels, format the value appropriately, and sort the chart by sales.

Exercise 3: Compare Products

Create a table containing Product, Total Quantity, and Total Sales. Identify the highest-selling product and verify the result by sorting the table.

Exercise 4: Apply a Visual-Level Filter

Filter the regional chart to show only North and West. Confirm whether the other visuals remain unchanged.

Exercise 5: Apply a Page-Level Filter

Apply a date filter to a report page and check whether all relevant visuals on that page reflect the selected period.

Exercise 6: Apply a Report-Level Filter

Apply a suitable report-level filter and inspect its effect across report pages. Record which visuals change and why.

Exercise 7: Create a Slicer

Add a Region slicer and test every region. Verify that the card, regional chart, trend chart, and table respond correctly.

Exercise 8: Troubleshoot a Filter

Choose a field that does not affect a visual as expected. Investigate the filter scope, visual interactions, data types, and model relationships to identify the cause.

21. Mini Project: Interactive Sales Performance Report

Project Objective: Build a report that helps a sales manager understand revenue, product performance, and regional trends.

21.1 Dataset Requirements

• Order ID
• Order Date
• Product Name
• Product Category
• Region
• Quantity
• Unit Price
• Sales Amount

21.2 Required Measures

Total Sales = SUM(Sales[Sales Amount])
Total Quantity = SUM(Sales[Quantity])
Order Count = DISTINCTCOUNT(Sales[Order ID])

These measures assume the table is named Sales and that the columns contain appropriate data types. Order Count returns the number of distinct order identifiers; the result depends on the uniqueness and quality of the identifier.

21.3 Required Visuals

• A card for Total Sales.
• A card for Total Quantity.
• A card for Order Count.
• A bar chart for Sales by Region.
• A line chart for Monthly Sales.
• A table for Product Name, Total Quantity, and Total Sales.
• A slicer for Region.
• A date filter or date slicer for the reporting period.

21.4 Project Validation Checklist

• All visuals use the intended fields and measures.
• Numeric aggregations are appropriate.
• Dates are stored and analyzed correctly.
• Region and date selections produce expected results.
• Filter scope is appropriate for each requirement.
• Visual interactions have been tested.
• Totals are reconciled against the source data.
• Titles, labels, units, and number formats are clear.
• The report is readable and does not contain unnecessary visual clutter.

22. Interview Questions and Answers

Q1. What is the Data pane in Power BI?

Answer: The Data pane lists the tables and fields available in the semantic model. It allows users to locate columns, measures, and other fields and add them to report visuals.

Q2. What is the purpose of the Visualizations pane?

Answer: It helps users select visual types and configure how data is displayed, including field assignments and formatting options supported by the selected visual.

Q3. What is the purpose of the Filters pane?

Answer: The Filters pane allows users to apply filters at visual, page, and report levels so that reports display the relevant subset of data.

Q4. What is the difference between a column and a measure?

Answer: A column represents row-level data, while a measure calculates a result based on the current evaluation context. Measures are commonly used for totals, ratios, and key performance indicators.

Q5. What is a visual-level filter?

Answer: It restricts the data used by a specific visual without automatically applying the same restriction to every other visual on the page.

Q6. What is a page-level filter?

Answer: It applies a filtering condition to relevant visuals on a particular report page.

Q7. What is a report-level filter?

Answer: It applies a filter across the report's relevant pages within the applicable filter context.

Q8. What is the difference between a filter and a slicer?

Answer: Filters are configured through filter controls, commonly in the Filters pane. A slicer is a visual placed on the canvas that lets users interactively select values.

Q9. Why might a chart show an unexpected total?

Answer: The chart may lack a category field, use an unsuitable aggregation, contain duplicate data, or be affected by filters or model relationships.

Q10. Why does a slicer not affect a particular visual?

Answer: The visual interaction may be disabled, the fields may not be connected through appropriate relationships, or the model may not support the expected filter propagation.

Q11. Which visual is generally suitable for trends over time?

Answer: A line chart is commonly suitable for showing how a measure changes over time.

Q12. Which visual is suitable for comparing sales by region?

Answer: A bar or column chart is generally suitable for comparing values across regions.

Q13. What is filter context?

Answer: Filter context is the set of filters that affects the calculation of a measure. It may come from visual categories, slicers, filter-pane settings, and relationships in the model.

Q14. What is Top N filtering?

Answer: Top N filtering restricts a visual to a specified number of highest- or lowest-ranked items based on a selected measure.

Q15. Why are data types important in Power BI?

Answer: Data types determine how fields are interpreted, which aggregations and operations are available, and how date, numeric, and text filters behave.

23. Quick Revision Notes

• The Data pane displays model tables and fields.
• Columns represent row-level data, while measures calculate results in context.
• The Visualizations pane helps create and format charts, tables, cards, and other visuals.
• Bar and column charts are useful for category comparisons.
• Line charts are commonly used to show trends over time.
• Cards highlight important single values.
• The Filters pane supports visual-level, page-level, and report-level filtering.
• Slicers provide visible, interactive selection controls on the report canvas.
• Filter scope determines which visuals are affected.
• Relationships influence how filters propagate across tables.
• Aggregation settings must match the intended business question.
• Validate totals and test interactions before publishing a report.

24. Final Checklist Before Publishing

• Confirm that all required fields are present and correctly named.
• Check data types and numeric aggregations.
• Verify all DAX measures against expected business definitions.
• Choose appropriate visuals for each analytical question.
• Format titles, axes, labels, and monetary values consistently.
• Review visual-level, page-level, and report-level filters.
• Test slicers and cross-visual interactions.
• Check model relationships if a filter behaves unexpectedly.
• Compare key totals with the source data.
• Ensure the report is readable and accessible.
• Save the report and publish it using the appropriate Power BI workflow.

25. Official Learning Resources

• Microsoft Learn: Tour of the Power BI report editor
• Microsoft Learn: Visualization types in Power BI
• Microsoft Learn: Filters and highlighting in Power BI reports
• JustAcademy: Microsoft Power BI Training
• JustAcademy: Register for a Course Demo
• JustAcademy Official Website

26. Conclusion

Working with the Data, Visualizations, and Filters panes is a fundamental skill for building effective Power BI reports. The Data pane helps users find and select fields, the Visualizations pane transforms those fields into useful charts and tables, and the Filters pane controls which data is included in each analytical view.

When these features are used together with appropriate data types, measures, model relationships, and visual interactions, users can create reports that are accurate, interactive, and easy to understand. Regular validation, clear formatting, and careful filter design help ensure that business users can trust the insights presented in a Power BI report.

To learn more about Power BI through JustAcademy, visit the Microsoft Power BI Training course page or register for a course demo.